What should library be

In my opinion it should have two parts: 
- macrolibrary which will be set on "macropack"s each containing set of macros
  solving with particular problem.
- routines library will be set of "routinepack"s (like window manipulating,
  opengl, I/O, OOP, etc.)

This way library will also replace Privalov's standard macros. We can save him
little part of his work this way.

I think library should preserve uniquity ad simplicity in FASM as much as
possible.



MACROLIBRARY:
- Each macropack will contain only and all macros solving particular problem
- There won't be more macropack on same problem (like another type of PROC or
  so). This could cause problems with routines using macros, and we should keep
  uniquity of FASM
- On macropack won't include another, even if it requires it. Every macropack
  will declare kind-of constant and another macropack using it will first check
  for this constant and prompt user to includ it. This way user knows what he 
  is using. Of course there can be ugly include-all files, but user at least
  has possiblity to stay clear. Just look at C's "windows.h".

ROUTINES LIBRARY:
- Routinepack is not dividable (eg. you have to include it whole)
? more routinepacks on same problem? How to solve it if user includes both?
- Routinepack doesn't include macropacks it uses, it only checks for them and
  promts user to include them if they aren't
- Routinepack doesn't include routinepacks either
- Routinepack will define all equates it for user
? Will routinepacks declare variables to be directly accessed by user?
- Routinepack can declare additional macros
